Update Gateway API to v1.3.0, target Envoy Gateway v1.5.0.#48
Merged
Conversation
Updated e2e test to avoid assertion failure on the `OverlappingTLSConfig` condition. Future work will be done to remove the v4 and v6 hostnames from being programmed on Gateways, which will remove this condition.
Due to limitations in how Envoy Gateway programs listeners, a ClientTrafficPolicy cannot be applied to non-TLS listeners with overlapping ports. Application to TLS listeners works without issue, however the inconsistency is undesirable. Future TLS settings can be provided via the Gateway Listener's TLS configuration. Header manipulation, while not "early", can be accomplished today via `RequestHeaderModifier` filters. Timeouts can also be defined in existing route rules. Remaining features are mostly around tuning, where there can be generous defaults set on the platform.
scotwells
approved these changes
Sep 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated e2e test to avoid assertion failure on the
OverlappingTLSConfigcondition. Future work will be done to remove the v4 and v6 hostnames from being programmed on Gateways, which will remove this condition.Related work: